Skip to main content

Input Sensitive Information Management

By registering regular expressions, sensitive information is protected by controlling the text input by users in the business system (app/URL input field).

Input Prompt Firewall Guide​

Input sensitive information checkInput Prompt FirewallAs part of the (old custom overlay), it checks and controls sensitive information in the input content before the user inputs and transmits it to external services such as generative AI.

Core Values

  • Prevention: Unlike the existing method that detects after transmission, it inspects and blocks before the input is sent externally.
  • Original text not leaked: Designed to only transmit results that have passed inspection, preventing sensitive information from being sent to external services or remote screens.
  • Bypass Blocking: Perform inspection and judgment at a control point rather than the user local, blocking bypassing inspections by local tampering.
  • Judgment·Record: It determines whether the text file is allowed or blocked, and logs the entire process in an audit log.

Screen Layout Guide​

The screen configuration of this menu varies according to the input sensitive information inspection method (input prompt firewall) settings. Please refer to the tabs visible on the current screen.

  • [Regular Expression] When both the [Conditional Policy] tab and the [Regular Expression] tab are visible(Basic)
    • Register the regular expression according to the instructions in this guide, and set the input sensitive information policy in the [Conditional Policy] tab.
  • [Regular Expression] When Only Tabs Are Visible
    • You can register regular expressions in this menu.
    • Input sensitive information inspection usage status and targets are conditional policies of the business system (app / URL input field).Isolation Security Policy > Data Security > Input Sensitive Information InspectionSet in.
  • If this menu is not visible
    • This is a configuration that uses external inspection systems to check sensitive input information. There are no items to be set separately on the admin page.

The screen configuration is determined by the inspection method set during the company's introduction and is not changed in the admin page. If configuration changes are needed, please contact the person in charge of the introduction or the operator.

Registering Regular Expressions​

1. Start of regular expression registration​

  1. Click on the "Sensitive Information Management" submenu under the business system.
  2. Click the [+Regular Expression Registration] button.
  3. The "Register Regular Expression" slide panel opens on the right.

2. Basic Information on Regular Expressions​

Name (required)

  • Enter a name that can identify the regular expression
  • Example: "Resident Registration Number", "Credit Card Number", "Mobile Phone Number" etc.

Description (Optional)

  • Detailed explanation of the corresponding regular expression.
  • Specifies what types of sensitive information are detected

3. Regular Expression Pattern Input (Required)​

Writing Regular Expressions

  • Enter the pattern of the sensitive information to be detected using regular expressions.

4. Regular Expression Test​

Test text input

  • Enter sample data in the "Regular Expression Test" input field.
  • You can check in real-time whether the entered regular expression matches correctly.

Check Matching Results

  • When matching with the regular expression: display success message
  • When the regular expression does not match: Display the error message "An unmatched regular expression has been entered."
  • A complete pattern must match to be recognized as correct.

5. Saving Regular Expressions​

  • After entering all the information and completing the test, click the [Register] button.
  • Clicking the [Cancel] button will close the panel without saving the entered content.

Standard Regular Expression Examples (Reference)​

Common regular expressions for detecting sensitive information. They are written in a syntax compatible with common regex engines (PCRE/JS/Java/.NET), and due to DLP characteristics, they are designed to minimize false negatives while allowing for some false positives.**Each pattern should be validated using the "Regular Expression Test" feature above by inputting a sample before registration.**Hello.

*Note: Currently\bis not available due to issues in functionality implementation. Explicitly\bto(?<![A-Za-z0-9_])...(?![A-Za-z0-9_])You can use it.

divisionSensitive InformationRegular ExpressionMatching ExampleNote
Personal IdentificationResident Registration Number\d{6}[-\s]?[1-4]\d{6}900101-1234567Gender Position 1~4. Including Foreigners[1-8]. Date validation precision type is referenced below
Personal IdentificationForeign Registration Number\d{6}[-\s]?[5-8]\d{6}900101-5234567Constellation 5~8
Personal IdentificationPassport Number (Korea)(?<![A-Za-z0-9_])[A-Z]\d{8}(?![A-Za-z0-9_])M12345678English character 1 + number 8
Personal IdentificationDriver's License Number\d{2}-?\d{2}-?\d{6}-?\d{2}11-22-123456-7812 digits. Adjustments based on environmental variations in regional and issuance format.
Communicationmobile phone number01[016789][-\s]?\d{3,4}[-\s]?\d{4}010-1234-5678010/011/016~019
CommunicationLandline/Main Phone0\d{1,2}[-\s]?\d{3,4}[-\s]?\d{4}02-1234-5678Including area code. Possible matching duplicates with mobile phones.
accountemail address[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}user@example.comPractical Standard Type (Not Entirely RFC5322)
FinanceCredit Card (16 digits)\d{4}[-\s]?\d{4}[-\s]?\d{4}[-\s]?\d{4}1234-5678-9012-3456Luhn validation is not possible with regular expressions. Refer to the patterns by brand below.
OrganizationBusiness Registration Number\d{3}-?\d{2}-?\d{5}123-45-678903-2-5, 10 digits
organizationCorporate Registration Number\d{6}-?\d{7}110111-12345676-7, 13 digits
NetworkIPv4 Address(?<![A-Za-z0-9_])(\d{1,3}\.){3}\d{1,3}(?![A-Za-z0-9_])192.168.0.1Loose matching. Octet 0~255 strict type is referenced below.
NetworkMAC address([0-9A-Fa-f]{2}[:-]){5}[0-9A-Fa-f]{2}00:1A:2B:3C:4D:5EColon/Hyphen Separator

Precision·Expansion Pattern (Optional)

pipe(|) is a precise pattern that is difficult to include in a table. Use it instead of the basic form above if necessary.

# Resident Registration Number — Month (01~12)·Day (01~31) Range Validation
\d{2}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])[-\s]?[1-4]\d{6}

# IPv4 — Each Octet 0~255 Strict
(?<![A-Za-z0-9_])((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.){3}(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(?![A-Za-z0-9_])

# Credit Card — By Brand (Based on IIN)
Visa              4\d{12}(\d{3})?
Mastercard        5[1-5]\d{14}
American Express  3[47]\d{13}

The above pattern is a widely used standard form, but adjustments may be necessary depending on the introduction environment and policy objectives. Items with significant format variations, such as driver's licenses, landline phones, and account numbers, particularly require environmental verification. Be sure to verify through the testing function within the product before registration.

Managing Regular Expression List​

Each regular expression is managed with a unique name, and can be selected and used from this list when configuring policies later.

Setting Input Sensitive Information Policy​

After registering the regular expression, you can set the following detailed conditions through separate policy settings:

1. Policy Basic Information​

  • Policy Name: A name that can identify the policy
  • Members: Target members to which the policy will apply
  • Description: Detailed description of the policy

2. Select Target System​

  • All business systems: Apply policies to all registered business systems
  • Specific Work System: Directly enter the URL to apply only to a specific system

3. Regular Expression Selection​

  • Select a pattern to apply from the pre-registered list of regular expressions.
  • You can select and use multiple regular expressions.

4. Setting Conditions​

  • Location Conditions: Apply policy only at specific locations
  • Time Condition: Apply policy only during specific time zones
  • Device Conditions: Apply policy only on specific device types

5. Audit Policy​

  • Log Recording Options: Log only blocked or log both allow and block
  • Log Detail: Whether to include user input text content

6. Policy Activation​

  • Settings: Policy Activation/Deactivation Status
  • Expiration Date: Policy Application Period Setting

Policy List Management​

Check Policy List​

The registered policies are displayed in a list.

Setting Policy Priorities​

  1. You can change the order of policies by dragging and dropping them in the policy list.
  2. The higher the order, the higher the priority.
  3. When multiple policies can be applied simultaneously, the policies with higher priority are processed first.

Policy Modification and Deletion​

  • You can select a registered policy to modify or delete.
  • When modifying the policy, the same settings screen will appear.

Log Records​

  • All detection and blocking events are logged according to the configured audit policy.
  • When text matching the regular expression is detected, it is immediately blocked and logged.
  • The log includes time, user, applied policy, detected content, etc.